Re: syslogd

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Steve Chew: "Re: Not so much a bug as a warning of new brute force attack"
• Previous message: simes@tcp.co.uk: "Re: Attacks using pop"

"PEM" == Perry E Metzger <perry@piermont.com> writes:

>> >What solutions have people used to restrict which hosts can send stuff
>> >to their syslogd?

PEM> I hacked NetBSD's syslogd so that with an option it only opens the
PEM> unix domain socket and not the UDP socket. The code is in the main
PEM> NetBSD sources.

Greg Wettstein's newest release (1.3) of syslogd for Linux does not do
UDP-based logging unless it is specifically requested on the
command-line.  Its default mode now is to only do local logging.


* By default the syslog daemon doesn't accept any message from the
  syslog/udp port. To enable this add "-r" to the command-line
  arguments.

Seems like more and more people are starting to worry about this.  :)~

--Up.

--
Jeff Uphoff - systems/network admin.  |  juphoff@nrao.edu
National Radio Astronomy Observatory  |  juphoff@bofh.org.uk
Charlottesville, VA, USA              |  jeff.uphoff@linux.org
    PGP key available at: http://www.cv.nrao.edu/~juphoff/

• Next message: Steve Chew: "Re: Not so much a bug as a warning of new brute force attack"
• Previous message: simes@tcp.co.uk: "Re: Attacks using pop"